Policy node identifier for application services in a packet core network

ABSTRACT

Node identifiers can be assigned to packet core policy nodes and directly routed to a diameter routing agent (DRA) and application functions (AFs) within a call processing message that is employed to establish an application service. Such a policy node identity will be received by Application Functions, UEs and/or intermediate message routers during the initial establishment of a packet data session so that they can refer to the policy node entity directly in the sub-sequent call processing flows related the established session, instead of querying a relational database which can be complex to maintain with multi-million correlation records. As an example, the policy node identifiers can be configurable and can comprise a hostname of the policy nodes, address data associated with the policy nodes, or a defined numerical value that maps to the hostname of the policy nodes.

TECHNICAL FIELD

The subject disclosure relates to wireless communications, e.g., policynode identifier utilized for application services in a packet corenetwork.

BACKGROUND

Long Term Evolution (LTE) networks support a large number of applicationservices (e.g. voice over LTE (VoLTE), video streaming and/or downloadservices, content delivery services, etc.) and will continue to add newrevenue-generating services (e.g. dynamic traffic management). Withmobile data and voice traffic growing exponentially, service reliabilityhas become a crucial factor for the LTE network. Moreover, it isimportant that services are delivered seamlessly, and servicedisruptions are avoided.

In conventional systems, when a user equipment (UE) attaches to an LTEnetwork and initiates application service, several packet core nodes areemployed in the call flow for service delivery, such as, a mobilitymanagement entity (MME), a serving and packet gateway (S/PGW), adiameter routing agent (DRA), a policy and charging rules function(PCRF) and an application function (AF). During a UE attach procedure,the MME sends a Create Session Request to the S/PGW, which then sends aCredit Control Request (CCR-I) to the PCRF via the DRA. The PCRFresponds to S/PGW with a Credit Control Answer (CCA-I) and the S/PGWthen sends Create Session Response to the MME. Traditionally, the DRAstores the PCRF routing information per Internet protocol-connectivityaccess network (IP-CAN) session in a binding database. This routinginformation is critical for delivering application services. Forapplication services to be established, an Rx message comprising anidentifier of the UE is sent from the AF to the DRA. The DRA can thendetermine the PCRF hosting the IP-CAN session by querying the bindingdatabase.

Typically, the binding database comprises millions of records.Management and maintenance of such a large number of records can becomplex. Further, unavailability of this binding database can directlyimpact application services and result in substantial revenue loss.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example system that facilitates establishment ofapplication services based on routing of node identifier data.

FIGS. 2A-2D illustrate an example message sequence flow chart thatdeploys a policy node identifier in packet core network devices.

FIGS. 3A-B illustrate an example message sequence flow chart thatdeploys a policy node identifier in user equipment (UEs).

FIG. 4 illustrates an example system that routes node identifiers to adiameter routing agent (DRA) to facilitate policy and charging rulesfunction (PCRF) selection.

FIG. 5 illustrates example system that facilitates configuration of nodeidentifiers.

FIG. 6 illustrates an example system that facilitates a generation of aglobal mapping table in accordance with the subject embodiments.

FIG. 7 illustrates an example method that efficiently determines a hostpolicy node during establishment of a dedicated bearer.

FIG. 8 illustrates an example method that facilitates a detection of ahost policy node based on a transfer of identifier data to a UE.

FIG. 9 illustrates a block diagram of a computer operable to execute thedisclosed communication architecture.

FIG. 10 illustrates a schematic block diagram of a computing environmentin accordance with the subject specification

DETAILED DESCRIPTION

One or more embodiments are now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the various embodiments. It may be evident,however, that the various embodiments can be practiced without thesespecific details, e.g., without applying to any particular networkedenvironment or standard. In other instances, well-known structures anddevices are shown in block diagram form in order to facilitatedescribing the embodiments in additional detail.

As used in this application, the terms “component,” “module,” “system,”“interface,” “node,” “platform,” “server,” “controller,” “entity,”“element,” “function,” “gateway,” “agent,” or the like are generallyintended to refer to a computer-related entity, either hardware, acombination of hardware and software, software, or software in executionor an entity related to an operational machine with one or more specificfunctionalities. For example, a component may be, but is not limited tobeing, a process running on a processor, a processor, an object, anexecutable, a thread of execution, computer-executable instruction(s), aprogram, and/or a computer. By way of illustration, both an applicationrunning on a controller and the controller can be a component. One ormore components may reside within a process and/or thread of executionand a component may be localized on one computer and/or distributedbetween two or more computers. As another example, an interface cancomprise input/output (I/O) components as well as associated processor,application, and/or API components.

Further, the various embodiments can be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement one or moreaspects of the disclosed subject matter. An article of manufacture canencompass a computer program accessible from any computer-readabledevice or computer-readable storage/communications media. For example,computer readable storage media can comprise but are not limited tomagnetic storage devices (e.g., hard disk, floppy disk, magnetic strips. . . ), optical disks (e.g., compact disk (CD), digital versatile disk(DVD) . . . ), smart cards, and flash memory devices (e.g., card, stick,key drive . . . ). Of course, those skilled in the art will recognizemany modifications can be made to this configuration without departingfrom the scope or spirit of the various embodiments.

In addition, the word “example” or “exemplary” is used herein to meanserving as an example, instance, or illustration. Any aspect or designdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects or designs. Rather, use ofthe word exemplary is intended to present concepts in a concretefashion. As used in this application, the term “or” is intended to meanan inclusive “or” rather than an exclusive “or.” That is, unlessspecified otherwise, or clear from context, “X employs A or B” isintended to mean any of the natural inclusive permutations. That is, ifX employs A; X employs B; or X employs both A and B, then “X employs Aor B” is satisfied under any of the foregoing instances. In addition,the articles “a” and “an” as used in this application and the appendedclaims should generally be construed to mean “one or more” unlessspecified otherwise or clear from context to be directed to a singularform.

Moreover, terms like “user equipment,” “mobile station,” and similarterminology, refer to a wired or wireless communication-capable deviceutilized by a subscriber or user of a wired or wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Data and signaling streams can be packetized orframe-based flows. Further, the terms “user,” “subscriber,” “consumer,”and the like are employed interchangeably throughout the subjectspecification, unless context warrants particular distinction(s) amongthe terms. It should be noted that such terms can refer to humanentities or automated components supported through artificialintelligence (e.g., a capacity to make inference based on complexmathematical formalisms), which can provide simulated vision, soundrecognition and so forth.

It should be noted that although various aspects and embodiments havebeen described herein in the context of 5G and/or long term evolution(LTE), or other next generation networks, the disclosed aspects are notlimited to 5G, a UMTS implementation, and/or an LTE implementation asthe techniques can also be applied in 3G or other network systems. Forexample, aspects or features of the disclosed embodiments can beexploited in substantially any wireless communication technology. Suchwireless communication technologies can include universal mobiletelecommunications system (UMTS), code division multiple access (CDMA),Wi-Fi, worldwide interoperability for microwave access (WiMAX), generalpacket radio service (GPRS), enhanced GPRS, third generation partnershipproject (3GPP), LTE, third generation partnership project 2 (3GPP2)ultra mobile broadband (UMB), high speed packet access (HSPA), evolvedhigh speed packet access (HSPA+), high-speed downlink packet access(HSDPA), high-speed uplink packet access (HSUPA), Zigbee, or anotherIEEE 802.XX technology. Additionally, substantially all aspectsdisclosed herein can be exploited in legacy telecommunicationtechnologies.

As used herein, “5G” can also be referred to as New Radio (NR) access.Accordingly, systems, methods, and/or machine-readable storage media forfacilitating improved communication coverage for 5G systems are desired.As used herein, one or more aspects of a 5G network can comprise, but isnot limited to, data rates of several tens of megabits per second (Mbps)supported for tens of thousands of users; at least one gigabit persecond (Gbps) to be offered simultaneously to tens of users (e.g., tensof workers on the same office floor); several hundreds of thousands ofsimultaneous connections supported for massive sensor deployments;spectral efficiency significantly enhanced compared to 4G; improvementin coverage relative to 4G; signaling efficiency enhanced compared to4G; and/or latency significantly reduced compared to LTE.

Conventional evolved pack core (EPC) networks rely on a binding databasecoupled to a diameter routing agent (DRA) to forward an applicationrequest to the correct Policy and Charging Rules Function (PCRF) thathosts a session related to the application request. In particular, theDRA binding database comprises records for PCRF routing information perIP connectivity access network (IP-CAN) session. Thus, each userequipment (UE) coupled to the packet core network can have multiplerecords stored in the binding database (e.g., a first record forinternational mobile subscriber identity (IMSI)+access point name (APN),a second record for mobile station international subscriber directorynumber (MSISDN)+APN, a third record for Internet Protocol version 6(IPv6)). Accordingly, the binding database for a large communicationnetwork can comprise millions of records. Unavailability of this bindingdatabase can cause application service outage, resulting in asignificant revenue loss. Moreover, without the binding database, thereis no way for the DRA to process incoming application service requestsand route the requests to appropriate host PCRFs. For example, when abinding database is not available, and a UE initiates a voice over LTE(VoLTE) call, the VoLTE call will fail until the binding database isrestored. The same is true for other application services as well. Toovercome these challenges, the systems and methods disclosed hereinrelate to processing application service requests without implementingand/or employing a DRA binding database. In contrast with conventionalsystems, the systems and methods disclosed herein utilize nodeidentifiers assigned to packet core nodes and route the node identifiersto the DRA within a call flow message that is employable to establish anapplication service.

Referring initially to FIG. 1, there illustrated is an example system100 that facilitates an establishment of application services based onrouting of node identifier data, according to one or more aspects of thedisclosed subject matter. In one aspect, system 100 enables a DRA 102 toaccurately determine a policy node, for example, a host PCRF 104, forestablishing a dedicated bearer for an application service requested bya UE 106. As an example, the UE 106 can comprise, but is not limited to,most any industrial automation device and/or consumer electronic device,for example, a tablet computer, a digital media player, a wearabledevice, a digital camera, a media player, a cellular phone, a personalcomputer, a personal digital assistant (PDA), a smart phone, a laptop, agaming system, set top boxes, home security systems, an Internet ofthings (IoT) device, a connected vehicle, at least partially automatedvehicle (e.g., drones), etc. System 100 can be part of most anycommunication network, such as, but not limited to an LTE network, a 5Gnetwork and/or other next-generation networks.

The DRA 102 is employed to provide real-time routing functions thatallow messages to be routed to the correct network devices. In oneaspect, the DRA 102 can facilitate session binding (e.g., in IP-CANsessions) towards the PCRF 104. Moreover, the session binding isutilized to handle multiple Diameter sessions in application services.For example, in VoLTE services, the LTE parts of a VoLTE call, togetherwith the IP Multimedia Subsystem (IMS) parts of the call, are controlledby the same PCRF (e.g., PCRF 104). Additionally, consistent policy rulesneed to be applied to the session that are related to the same VoLTEcall. The PCRF 104 can be utilized to implement policy control decisionand flow-based charging control functionalities. The PCRF 104 canprovide network control regarding the service data flow detection,gating, quality of service (QoS) and flow-based charging towards apolicy and charging enforcement function (PCEF) (not shown). Anapplication function (AF) 114, can provide session and media relatedinformation to the PCRF 104, which in turn can notify the AF 114 oftraffic plane events. In case of VoLTE, the PCRF 104 can communicatewith devices of the IMS network for establishing the VoLTE calls andallocating the requested bandwidth to the call bearer, for example, withconfigured attributes.

When UE 106 initially registers with the network, for example via anaccess network 108, a default bearer is established for communicatingwith the network or applications. As part of UE attach procedure, theserving MME (e.g., MME 110) sends a request (e.g., create sessionrequest (CSR)) to the serving and packet data network gateway (PGW)(e.g., S/PGW 112), which then sends a request (e.g., a Gx credit controlrequest (CCR-I)) to a host PCRF 104 via the DRA 102. The host PCRF 104can respond to the request (e.g., by transmitting a Gx credit controlanswer (CCA-I)) and initiate establishment of the default bearer. Whenthe UE 106 initiates an application service (e.g., makes a VoLTE call)via application function (AF) 114 (e.g., proxy-call session controlfunction (P-CSCF) in case of VoLTE service), the same PCRF that wasemployed to establish the default bearer (e.g., PCRF 104) is to beutilized to establish a dedicated bearer for the application service.

According to an aspect, to ensure that the host PCRF 104 is accuratelydetermined during application service establishment, system 100facilitates routing of identifier information associated with the packetcore nodes (e.g., PCRF 104, S/PGW 112, etc.). For example, the nodeidentifiers for PCRF 104 and S/PGW 112 can be introduced into theend-to-end application call flow. In an aspect, the node identifiers areconfigurable and can be assigned as the hostname of the node or most anydefined identifier (e.g., 16-bit identifier). In one aspect, duringestablishment of the default bearer, the PCRF 104 can transmit itsidentifier to the S/PGW 112 via the DRA 102. For example, the identifiercan be included within and/or appended to a Gx CCA-I message. In anotherexample, the identifier can be transmitted within a new message. In oneembodiment, the node identifiers can be deployed in the core network,such that on default bearer establishment, the S/PGW 112 can notify theAF 114 with node identifier for the PCRF 104 as well as the S/PGWs 112'sidentifier. In this example scenario, the AF 114 can store theidentifiers and provide them to the DRA 102 on receiving an applicationservice request from the UE 106. The DRA 102 can utilize the identifiersto direct the request to the appropriate host PCRF 104 to facilitateestablishment of the dedicated bearer for the application service.

In another embodiment, the node identifiers can be extended to the UE106, such that on default bearer establishment, the S/PGW 112 can relaythe node identifiers to the UE 106. In this example embodiment, theidentifiers can be stored within the UE 106 and can be transmitted tothe AF 114 within (and/or along with) an application service request.The AF 114 can then forward the identifiers to the DRA 102, which canutilize the identifiers to direct the request to the appropriate hostPCRF 104 to facilitate establishment of the dedicated bearer for theapplication service. These embodiments enable the DRA 102 to efficientlydetermine host PCRFs independent of using and/or maintaining a largebinding database.

It is noted that the network functions shown in the figures are forillustration purposes and that the subject embodiment architecture canbe extended to other network implementations. For example, the FIG. 1shows the combined Serving GW and Packet GW (e.g., S/PGW 112). However,the implementation can also combine the MME 110 with the SGW and PGW(e.g., S/PGW 112) is an independent network function. This principleapplies to any wireless network implementation variations.

Referring now to FIGS. 2A-D, there illustrated is an example end-to-endapplication call flow (200, 225, 250, 275) that deploys a policy nodeidentifier in packet core network devices, in accordance with an aspectof the subject disclosure. It is noted that the DRA 102, PCRF 04, UE106, S/PGW 112, and AF 114 can comprise functionality as more fullydescribed herein, for example, as described above with regard to system100. Although the call flow (200, 225, 250, 275) has been described withrespect to an LTE network, it is noted that the subject disclosure isnot limited to LTE networks and can be utilized in most anycommunication network.

FIGS. 2A-D provide an easy-to-deploy solution that provides an efficientway to find the correct PCRF (e.g., host PCRF for a session) whileminimizing service impact to end-user or application. According to anaspect, the core network policy nodes, for example, PCRF 104 and S/PGW112, can be assigned respective identifiers within the network. In anexample, the identifiers can comprise 16 bits. In another example, theidentifier can comprise, but is not limited to, a hostname of the node,a numeric number, IP address, or a L2 link address. According to anaspect, end-to-end application call flows can be modified to transferthe identifier data during the call flow to facilitate PCRFdetermination. In an aspect, a SGi interface between S/PGW and P-CSCFcan be utilized to convey and/or update the identifier data.

Referring to FIG. 2A, when UE 106 attaches to the network (e.g., duringpower up, entry within a coverage area of the network, etc.), a request(e.g., CSR) is sent from the MME (shown in FIG. 1) to the S/PGW 112. Asdepicted at (1), the S/PGW 112 sends a request (e.g., Gx CCR-I) toestablish a default bearer, to the DRA 102, which can then determine aPCRF, for example, PCRF 104 to service the request. At (2), the DRArelays the request (e.g., Gx CCR-I) to the PCRF 104. At (3), the PCRF104 transmits a response (e.g., Gx CCA-I (with PCRF ID)) to the DRA 102.In one aspect, PCRF 104's identifier is included within and/or appendedto the response. At (4), the DRA 102 can relay the response (and PCRFID) to the S/PGW 112, which can then send a create session response toMME to facilitate establishment of a default bearer for the UE 106.

Referring to FIG. 2B, when the response (e.g., Gx CCA-I (with PCRF ID))is received from the PCRF 104 and the default bearer is successfullyestablished, at (5) the S/PGW 112 can send a notify message (e.g.,in-band and/or out-of-band) to AF 114. As an example, the notify messagecan comprise information, such as, but not limited to, bearerinformation, the PCRF ID, and the S/PGW 112's identifier (e.g., PGW ID).Alternatively, the identifiers (e.g., PCRF ID and PGW ID) can betransmitted within (and/or appended to) a session initiation protocol(SIP) Register message. In one aspect, an existing link between theS/PGW 112 and the AF 114 can be leveraged to transfer the identifiers.The AF 114 can store the transferred information within its data storeand at (6) can transmit an acknowledge message back to the S/PGW 112.

Referring now to FIG. 2C, when an application service is to beinitiated, (e.g., at (7) UE 106 can send a SIP INVITE message to AF114), the AF 114 can determine the stored PCRF and PGW identifiers andgenerate a Rx AA-Request (AAR) that comprises the PCRF and PGWidentifiers. In case the notify message is not received at the time ofthe SIP INVITE message arrival, at (7 a) the AF 114 can pull the nodeidentifiers from the S/PGW 112 to avoid any race conditions. At (8), theAF 114 can transfer the Rx AAR and the PCRF and PGW identifiers to theDRA 102. The DRA 102 can identify the PCRF hostname from the receivedPCRF identifier and at (9) route the message to the correct PCRF. Sincethe destination node information is provided in the Rx AAR, theimplementation and/or maintenance of a complex binding database can beavoided. At (10) and (11), an Rx AA Answer (AAA) message can betransferred from the PCRF 104 to the AF 114 via the DRA 102.

FIG. 2D illustrates establishment of a dedicated bearer. The PCRF 104can determine a Gx session to which the incoming Rx AAR should be bound.Further, the PCRF 104 can create charging rules and at (12) and (13)send a message (e.g., Gx RAR) to S/PGW 112 via the DRA 102. At (14) and(15), the S/PGW 112 can respond (e.g., Gx RAA) to the PCRF 104 via theDRA 102. Further, the S/PGW 112 can then establish a dedicated bearerfor the application service associated with (e.g., initiated by) UE 106.

Referring now to FIGS. 3A-B, there illustrated an example end-to-endapplication call flow (300,350) that deploys policy node identifier inUEs, in accordance with an aspect of the subject disclosure. FIGS. 3A-Bprovide a long-term solution that delivers an efficient way for a DRA102 to find the correct PCRF while eliminating a dependency oncentralized binding database comprising millions of records. It is notedthat the DRA 102, PCRF 04, UE 106, S/PGW 112, and AF 114 can comprisefunctionality as more fully described herein, for example, as describedabove with regard to system 100. Although the call flow (300, 350) hasbeen described with respect to an LTE network, it is noted that thesubject disclosure is not limited to LTE networks and can be utilized inmost any communication network that employs a policy driven servicearchitecture.

Similar to flow 200, when UE 106 attaches to the network (e.g., duringpower up, entry within a coverage area of the network, etc.), a request(e.g., create session request) is sent from the MME 110 to the S/PGW112. The S/PGW 112 can send a request to establish a default bearer(e.g., Gx CCR-I) to the DRA 102, which can then determine a destinationPCRF, for example, PCRF 104 to service the request. The DRA can thenrelay the request (e.g., Gx CCR-I) to the PCRF 104. At (1), the PCRF 104can transmit a response (e.g., Gx CCA-I (with PCRF ID)) to the DRA 102.In one aspect, PCRF 104's identifier can be included within and/orappended to the response. At (2), the DRA 102 can relay the response(and PCRF ID) to the S/PGW 112. In this embodiment, at (3), the S/PGW112 can transmit the response to the MME 110 along with the PCRF ID andthe S/PGW 112's identifier (PGW ID). For example, the PCRF and PGW IDscan be included as an information element (IE) in a GPRS tunnelingprotocol (GTP) create session response to MME 110. The MME 110 canfacilitate establishment of a default bearer for the UE 106. At (4), theMME 110 can send the PCRF and PGW IDs to the UE 106, for example, in anon-access stratum (NAS) message (e.g., ESM Message Container IE). Theidentifiers can be stored and maintained in a data store of the UE 106.

Referring to FIG. 3B, subsequent to the establishment of the defaultbearer, service requests (e.g., VoLTE SIP call) initiated by the UE 106can comprise the PCRF and PGW IDs (at (5)). At (6), the MME 110 canrelay the request and IDs to the S/PGW 112, which can provide therequest data (comprising the IDs) to the AF 114 (at (7)). The AF 114 caninclude/insert/append the PCRF ID attribute value pair (AVP) in adiameter request message that is transmitted to the DRA 102 (at (8)). Onreceipt of the request, the DRA 102 can query a global node identifierto hostname mapping table to identify the destination PCRF and at (9)route the message to the identified PCRF 104. It is noted that themapping table utilized by the DRA 102 is much smaller than aconventional binding database. Moreover, the mapping table simplycomprises one entry per PCRF coupled to the DRA, resulting in a tablewith much smaller entry sizes (<<1000 entries) depending on the carriernetwork size. In contrast, the conventional binding database comprisesmillions of records based on number of application sessions.Accordingly, since the mapping table is significantly smaller, the workperformed by DRA 102 for determining a destination PCRF is substantiallyreduced. In one example, the DRA 102 can dynamically maintain and/orupdate the mapping table by receiving information (e.g., periodically)from the PCRFs and/or other DRAs. At (10) and (11), an Rx AAA messagecan be transferred from the PCRF 104 to the AF 114 via the DRA 102. Adedicated bearer can then be established (e.g., as shown in call flow275).

It is noted that the call flow (200-275) depicted in FIGS. 2A-2D iseasier to deploy as compared to the call flow (330-35) depicted in FIGS.3A-3B since only the packet core nodes and their call flows are modifiedin 200-275, whereas 300-350 extends the node identifier deployment tothe MME and UE (e.g., which can typically take longer to implement).

Referring now to FIG. 4, there illustrated is an example system 400 thatroutes node identifiers to a DRA to facilitate PCRF selection, accordingto an aspect of the subject disclosure. It is noted that the DRA 102 andAF 114 can comprise functionality as more fully described herein, forexample, as described above with regard to systems 100-300. According toan aspect, policy network nodes (e.g., PCRF, PGW) can be assigned anidentifier in the network. As an example, the identifier can comprise ahostname, a numeric number, IP address, L2 link address, etc. In anotherexample, the identifier can comprise a 16-bit identifier that applies toa pool of nodes that share a common session database, wherein the higher8-bit can be reserved for a first node, for example, a PGW and the lower8-bit can be reserved for a second node, for example, a PCRF. Theidentifier can be configured and/or updated at most any time.

In a first embodiment, wherein changes are made only within the corenetwork (e.g., depicted in detail with respect to call flows 200-275),the identifier can comprise a hostname of the node. In this exampleembodiment, PGW and PCRF identifiers can be introduced into the defaultbearer establishment for a served UE, such that the PCRF can utilize aninterface between the PCRF and the PGW (e.g., Sgi interface) to conveyand/or update the identifiers. According to an aspect, an IDdetermination component 402 can receive identifier data (e.g., PCRF IDand PGW ID) from the PGW serving the UE. As an example, the identifierdata can be received in a push or pull configuration. In one aspect, theidentifier data can be received via in-band and/or out-of bandcommunication. In yet another aspect, the identifier data can bereceived via a SIP register message. The ID determination component 402can store the identifier data (e.g., linked to the UE/session/bearerinformation), within a data store 404. When determined that anapplication service is initiated by the UE (e.g., a SIP INVITE messageis received from the UE), an ID transmission component 406 can beutilized to transfer the identifier data (e.g., PCRF ID and PGW ID)associated with the UE to the DRA 102. As an example, the IDtransmission component 406 can insert/append the identifier datawithin/to an Rx AAR message. Alternatively, the ID transmissioncomponent 406 can transfer the identifier data via a new message. In anaspect, an ID extraction component 408 can extract the identifier datafrom the received message, a PCRF selection component 410 can determine(e.g., based on the PCRF hostname determined from the PCRF identifier) adestination PCRF to which the message (e.g., Rx AAR message) is to berelayed, and the DRA 102 can transmit the message to the determined PCRFto facilitate establishment of a dedicated bearer. Accordingly, the DRA102 can efficiently determine a destination PCRF without searchingthrough millions of records of a binding database.

In a second embodiment, wherein changes are extended to the MME and UE(e.g., depicted in detail with respect to call flows 300-350), theidentifier can comprise a 16-bit identifier that can map to a PGWhostname and a PCRF hostname. In this example embodiment, PGW and PCRFidentifiers can be introduced into the default bearer establishment fora served UE, such that the PCRF can utilize an interface between thePCRF and the PGW (e.g., Sgi interface) to convey and/or update the16-bit identifier and further, the PGW/serving gateway (SGW) can includethe identifier as an IE in a GTPv2-C Create Session Response to a MME,which in turn can send the identifier to the UE in a NAS Message (e.g.,ESM Message Container IE). The identifier can be stored and maintainedin the UE. Moreover, the UE can transmit the identifier in (and/or alongwith) subsequent service related messages (e.g. VoLTE SIP call) to theAF 114. On receiving the service related message, the ID determinationcomponent 402 can extract the identifier and the ID transmissioncomponent 406 can add the identifier, for example, as a node identifierAVP, in the diameter message and transmit the diameter message to theDRA 102. The ID extraction component 408 can receive the diametermessage and determine the node identifier AVP. Further, the PCRFselection component 410 can utilize the AVP to query a mapping table 412to determine the PCRF host name. In one example, the mapping table 412can store a mapping of node identifiers with hostnames of destinationnodes. Based on the PCRF host name, the DRA 102 can forward the diametermessage to the appropriate PCRF. This approach is very efficient infinding the right PCRF or policy node and eliminates the dependency oncentralized binding database which contains millions of records.

Referring now to FIG. 5, there illustrated is an example system 500 thatfacilitates configuration of policy node identifiers in accordance withthe subject embodiments. It is noted that the DRA 102, PCRF 104, andS/PGW 112 can comprise functionality as more fully described herein, forexample, as described above with regard to systems 100-400. According toan aspect, when node identifiers are extended to the MME and UE (e.g.,depicted in detail with respect to call flows 300-350), network nodes,such as PCRF 104 and S/PGW 112, can be configured with a commonidentifier to facilitate detection during dedicated bear establishment.As an example, the identifier can comprise a 16-bit identifier (e.g.,Hex) that can represent both the host S/PGW 112 and the host PCRF 104(e.g., eight bits reserved for each node). The identifier can bemaintained by node (e.g., PCRF 104 and/or S/PGW 112) and shared with theID configuration component 502, at most any time, such as, but notlimited to, during a node power-up, periodically, in response to anevent, on-demand, etc. The ID configuration component 502 can store theidentifier with corresponding node hostnames in the mapping table 412 asshown below:

TABLE 1 Node Identifier (hex) PCRF Host name PGW Host name 0x0101Pcrf01.host.name Pgw01.host.name 0x0202 Pcrf02.host.name Pgw02.host.name0x0303 Pcrf03.host.name Pgw03.host.name

As described in detail with regards to call flow 300-350, the identifieris transferred to the UE during default bearer establishment and thentransmitted by the UE to the AF during service initiation. The AFprovides the identifier to the DRA 102 as part of (and/or along with) adiameter request. Moreover, the DRA 102 can utilize the mapping table412 to determine hostnames for the nodes and select appropriate nodes,to which the diameter request is to be relayed (e.g., to facilitatededicated bearer establishment).

FIG. 6 illustrates an example system 600 that facilitates a generationof a global mapping table in accordance with the subject embodiments. Itis noted that the DRAs 602 ₁-602 _(N) (wherein N is most any integergreater than 1) are substantially similar to DRA 102 and can comprisefunctionality as more fully described herein, for example, as describedabove with regard to DRA 102. Further, PCRF/PGW 604 ₁-604 _(M) (whereinM is most any integer greater than 1) are substantially similar to PCRF104 and/or S/PGW 112 and can comprise functionality as more fullydescribed herein, for example, as described above with regard to PCRF104 and/or S/PGW 112. According to an embodiment, DRAs 602 ₁-602 _(N)can auto-learn (e.g., via a push or pull configuration) node identifierdata associated with connected nodes (e.g., PCRF/PGW 604 ₁-604 _(M)) andadd it to a global mapping table comprising a node identifier tohostname mapping (e.g., mapping table 412 within one or more of DRAs 602₁-602 _(N) and/or a network data store coupled to network 606).

FIGS. 7-8 illustrate flow diagrams and/or methods in accordance with thedisclosed subject matter. For simplicity of explanation, the flowdiagrams and/or methods are depicted and described as a series of acts.It is to be understood and noted that the various embodiments are notlimited by the acts illustrated and/or by the order of acts, for exampleacts can occur in various orders and/or concurrently, and with otheracts not presented and described herein. Furthermore, not allillustrated acts may be required to implement the flow diagrams and/ormethods in accordance with the disclosed subject matter. In addition,those skilled in the art will understand and note that the methods couldalternatively be represented as a series of interrelated states via astate diagram or events. Additionally, it should be further noted thatthe methods disclosed hereinafter and throughout this specification arecapable of being stored on an article of manufacture to facilitatetransporting and transferring such methods to computers. The termarticle of manufacture, as used herein, is intended to encompass acomputer program accessible from any computer-readable device orcomputer-readable storage/communications media.

Referring now to FIG. 7 there illustrated is an example method 700 thatefficiently determines a host policy node during establishment of adedicated bearer, according to an aspect of the subject disclosure. Inan aspect, method 700 can be implemented by one or more network devices(e.g., core network devices) of a communication network (e.g., cellularnetwork). At 702, network identifiers can be assigned to core networkpolicy nodes (e.g., PCRF and/or PGW). As an example, the networkidentifiers can comprise a hostname, a numeric value, an IP address, aL2 link address, etc. At 704, during default bearer establishmentassociated with a UE (e.g., when a UE powers on, enters the networkcoverage area, etc.), a policy node identifier, for example, a host PCRFID, can be conveyed to a gateway node, for example, a S/PGW. As anexample, the PCRF ID can be transmitted within and/or appended to a GxCCA-I message. When the default bearer is successfully established, at706, the host PCRF ID and a PGW ID can be transferred to an AF (e.g., aP-CSCF), for example, via in-band signaling, via out-of band signaling,via a SIP register message, etc.

Further, at 708 in response to determining that an application servicehas been initiated by the UE (e.g., based on receiving a SIP INVITEmessage from the UE), the host PCRF ID and PGW ID can be transferred toa DRA via a diameter request (e.g., Rx AAR message). At 710, based onthe received host PCRF ID, the diameter request can be relayed to anappropriate PCRF to facilitate an establishment of a dedicated bearerassociated with the application service.

FIG. 8 illustrates an example method 800 that facilitates a detection ofa host policy node based on a transfer of identifier data to a UE,according to an aspect of the subject disclosure. As an example, method800 can be implemented by one or more network devices of a communicationnetwork (e.g., cellular network). At 802, network identifiers can beassigned to core network policy nodes (e.g., PCRF and/or PGW). As anexample, the network identifiers can comprise a 16-bit identifier thatmaps to hostnames of the PCRF and/or PGW. At 804, during default bearerestablishment associated with a UE (e.g., when a UE powers on, entersthe network coverage area, etc.), identifier data associated with thepolicy nodes, for example, PCRF and PGW, can be conveyed to the UE via aMME. For example, the PGW can include the identifier data as an IE in aGTPv2-C Create Session Response to the MME, which in turn can send theidentifier data to the UE in a NAS Message (e.g., ESM Message ContainerIE). The identifier data can then be stored and maintained in the UE.

At 806, the identifier data can be received with (e.g., inserted withinand/or appended to) an application service request sent from the UE toinitiate an application service. For example, the UE can transmit a SIPINVITE message, that comprises the identifier data, to P-CSCF toinitiate a VoLTE call. In response to receiving the application servicerequest, at 808, the identifier data can be transferred to a DRA via adiameter request (e.g., Rx AAR message). Further, at 810, based on theidentifier data, a PCRF hostname can be retrieved from a mapping tableand the diameter request can be relayed to the appropriate PCRF tofacilitate an establishment of a dedicated bearer associated with theapplication service.

In one aspect, the systems 100-600 and methods 700-800 disclosed hereinprovide various non-limiting advantages, for example, (i) eliminatingdependence on a binding database to find the correct PCRF for AF; (ii)improving PCRF detection efficiency; (iii) minimizing service impact toend-user and/or application; (iv) addressing VoLTE and/or otherapplication service resiliency issues without utilizing a DRA bindingdatabase; (v) reducing cost and maintenance of DRA upgrade (e.g., sincea binding database is not required); (vi) enabling development of newapplication services; etc.

Referring now to FIG. 9, there is illustrated a block diagram of acomputer 902 operable to execute the disclosed communicationarchitecture. In order to provide additional context for various aspectsof the disclosed subject matter, FIG. 9 and the following discussion areintended to provide a brief, general description of a suitable computingenvironment 900 in which the various aspects of the specification can beimplemented. While the specification has been described above in thegeneral context of computer-executable instructions that can run on oneor more computers, those skilled in the art will recognize that thespecification also can be implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, applications (e.g., program modules) comprise routines,programs, components, data structures, etc., that perform particulartasks or implement particular abstract data types. Moreover, thoseskilled in the art will note that the inventive methods can be practicedwith other computer system configurations, comprising single-processoror multiprocessor computer systems, minicomputers, mainframe computers,as well as personal computers, hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices.

The illustrated aspects of the specification can also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

A computing device can typically include a variety of machine-readablemedia. Machine-readable media can be any available media that can beaccessed by the computer and includes both volatile and non-volatilemedia, removable and non-removable media. By way of example and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media can include volatileand/or non-volatile media, removable and/or non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules, orother data. Computer storage media can include, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, solid statedrive (SSD) or other solid-state storage technology, Compact Disk ReadOnly Memory (CD ROM), digital video disk (DVD), Blu-ray disk, or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed bythe computer. In this regard, the terms “tangible” or “non-transitory”herein as applied to storage, memory or computer-readable media, are tobe understood to exclude only propagating transitory signals per se asmodifiers and do not relinquish rights to all standard storage, memoryor computer-readable media that are not only propagating transitorysignals per se.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and comprises any informationdelivery or transport media. The term “modulated data signal” or signalsrefers to a signal that has one or more of its characteristics set orchanged in such a manner as to encode information in one or moresignals. By way of example, and not limitation, communication mediacomprise wired media, such as a wired network or direct-wiredconnection, and wireless media such as acoustic, radio frequency (RF),infrared and other wireless media. Combinations of the any of the aboveshould also be included within the scope of computer-readable media.

With reference again to FIG. 9, the example environment 900 forimplementing various aspects of the specification comprises a computer902, the computer 902 comprising a processing unit 904, a system memory906 and a system bus 908. As an example, the component(s),application(s) server(s), equipment, system(s), interface(s),gateway(s), controller(s), node(s), entity(ies), function(s), cloud(s),agent(s), entity(ies), and/or device(s) (e.g., DRA 102, PCRF 104, UE106, devices of network 108, MME 110, S/PGW 112, AF 114, IDdetermination component 402, ID transmission component 406, IDextraction component 408, PCRF selection component 410, ID configurationcomponent 502, DRAs 602 ₁-602 _(N), PCRF/PGW 604 ₁-604 _(M), devices ofnetwork 606, etc.) disclosed herein with respect to systems 100-500 caneach comprise at least a portion of the computer 902. The system bus 908couples system components comprising, but not limited to, the systemmemory 906 to the processing unit 904. The processing unit 904 can beany of various commercially available processors. Dual microprocessorsand other multi-processor architectures can also be employed as theprocessing unit 904.

The system bus 908 can be any of several types of bus structure that canfurther interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 906comprises read-only memory (ROM) 910 and random access memory (RAM) 912.A basic input/output system (BIOS) is stored in a non-volatile memory910 such as ROM, EPROM, EEPROM, which BIOS contains the basic routinesthat help to transfer information between elements within the computer902, such as during startup. The RAM 912 can also comprise a high-speedRAM such as static RAM for caching data.

The computer 902 further comprises an internal hard disk drive (HDD)914, which internal hard disk drive 914 can also be configured forexternal use in a suitable chassis (not shown), a magnetic floppy diskdrive (FDD) 916, (e.g., to read from or write to a removable diskette918) and an optical disk drive 920, (e.g., reading a CD-ROM disk 922 or,to read from or write to other high capacity optical media such as theDVD). The hard disk drive 914, magnetic disk drive 916 and optical diskdrive 920 can be connected to the system bus 908 by a hard disk driveinterface 924, a magnetic disk drive interface 926 and an optical driveinterface 928, respectively. The interface 924 for external driveimplementations comprises at least one or both of Universal Serial Bus(USB) and IEEE 1394 interface technologies. Other external driveconnection technologies are within contemplation of the subjectdisclosure.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 902, the drives and storagemedia accommodate the storage of any data in a suitable digital format.Although the description of computer-readable storage media above refersto a HDD, a removable magnetic diskette, and a removable optical mediasuch as a CD or DVD, it should be noted by those skilled in the art thatother types of storage media which are readable by a computer, such aszip drives, magnetic cassettes, flash memory cards, solid-state disks(SSD), cartridges, and the like, can also be used in the exampleoperating environment, and further, that any such storage media cancontain computer-executable instructions for performing the methods ofthe specification.

A number of program modules can be stored in the drives and RAM 912,comprising an operating system 930, one or more application programs932, other program modules 934 and program data 936. All or portions ofthe operating system, applications, modules, and/or data can also becached in the RAM 912. It is noted that the specification can beimplemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 902 throughone or more wired/wireless input devices, e.g., a keyboard 938 and/or apointing device, such as a mouse 940 or a touchscreen or touchpad (notillustrated). These and other input devices are often connected to theprocessing unit 904 through an input device interface 942 that iscoupled to the system bus 908, but can be connected by other interfaces,such as a parallel port, an IEEE 1394 serial port, a game port, a USBport, an IR interface, etc. A monitor 944 or other type of displaydevice is also connected to the system bus 908 via an interface, such asa video adapter 946.

The computer 902 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 948. The remotecomputer(s) 948 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallycomprises many or all of the elements described relative to the computer902, although, for purposes of brevity, only a memory/storage device 950is illustrated. The logical connections depicted comprise wired/wirelessconnectivity to a local area network (LAN) 952 and/or larger networks,e.g., a wide area network (WAN) 954. Such LAN and WAN networkingenvironments are commonplace in offices and companies, and facilitateenterprise-wide computer networks, such as intranets, all of which canconnect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 902 is connectedto the local network 952 through a wired and/or wireless communicationnetwork interface or adapter 956. The adapter 956 can facilitate wiredor wireless communication to the LAN 952, which can also comprise awireless access point disposed thereon for communicating with thewireless adapter 956.

When used in a WAN networking environment, the computer 902 can comprisea modem 958, or is connected to a communications server on the WAN 954or has other means for establishing communications over the WAN 954,such as by way of the Internet. The modem 958, which can be internal orexternal and a wired or wireless device, is connected to the system bus908 via the serial port interface 942. In a networked environment,program modules depicted relative to the computer 902, or portionsthereof, can be stored in the remote memory/storage device 950. It willbe noted that the network connections shown are example and other meansof establishing a communications link between the computers can be used.

The computer 902 is operable to communicate with any wireless devices orentities operatively disposed in wireless communication, e.g., desktopand/or portable computer, server, communications satellite, etc. Thiscomprises at least Wi-Fi and Bluetooth™ wireless technologies or othercommunication technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity networks use radio technologies called IEEE802.11 (a, b, g, n, etc.) to provide secure, reliable, fast wirelessconnectivity. A Wi-Fi network can be used to connect computers to eachother, to the Internet, and to wired networks (which use IEEE 802.3 orEthernet). Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radiobands, at an 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, forexample, or with products that contain both bands (dual band), so thenetworks can provide real-world performance similar to the basic 10BaseTwired Ethernet networks used in many offices.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “data store,” data storage,”“database,” “cache,” and substantially any other information storagecomponent relevant to operation and functionality of a component, referto “memory components,” or entities embodied in a “memory” or componentscomprising the memory. It will be noted that the memory components, orcomputer-readable storage media, described herein can be either volatilememory or nonvolatile memory, or can comprise both volatile andnonvolatile memory. By way of illustration, and not limitation,nonvolatile memory can comprise read only memory (ROM), programmable ROM(PROM), electrically programmable ROM (EPROM), electrically erasable ROM(EEPROM), or flash memory. Volatile memory can comprise random accessmemory (RAM), which acts as external cache memory. By way ofillustration and not limitation, RAM is available in many forms such assynchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM),double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), SynchlinkDRAM (SLDRAM), and direct Rambus RAM (DRRAM). Additionally, thedisclosed memory components of systems or methods herein are intended tocomprise, without being limited to comprising, these and any othersuitable types of memory.

Referring now to FIG. 10, there is illustrated a schematic block diagramof a computing environment 1000 in accordance with the subjectspecification. The system 1000 comprises one or more client(s) 1002. Theclient(s) 1002 can be hardware and/or software (e.g., threads,processes, computing devices).

The system 1000 also comprises one or more server(s) 1004. The server(s)1004 can also be hardware and/or software (e.g., threads, processes,computing devices). The servers 1004 can house threads to performtransformations by employing the specification, for example. Onepossible communication between a client 1002 and a server 1004 can be inthe form of a data packet adapted to be transmitted between two or morecomputer processes. The data packet may comprise a cookie and/orassociated contextual information, for example. The system 1000comprises a communication framework 1006 (e.g., a global communicationnetwork such as the Internet, cellular network, etc.) that can beemployed to facilitate communications between the client(s) 1002 and theserver(s) 1004.

Communications can be facilitated via a wired (comprising optical fiber)and/or wireless technology. The client(s) 1002 are operatively connectedto one or more client data store(s) 1008 that can be employed to storeinformation local to the client(s) 1002 (e.g., cookie(s) and/orassociated contextual information). Similarly, the server(s) 1004 areoperatively connected to one or more server data store(s) 1010 that canbe employed to store information local to the servers 1004.

What has been described above comprises examples of the presentspecification. It is, of course, not possible to describe everyconceivable combination of components or methods for purposes ofdescribing the present specification, but one of ordinary skill in theart may recognize that many further combinations and permutations of thepresent specification are possible. Accordingly, the presentspecification is intended to embrace all such alterations, modificationsand variations that fall within the spirit and scope of the appendedclaims. Furthermore, to the extent that the term “comprises” is used ineither the detailed description or the claims, such term is intended tobe inclusive in a manner similar to the term “comprising” as“comprising” is interpreted when employed as a transitional word in aclaim.

1. A system, comprising: a processor; and a memory that storesexecutable instructions that, when executed by the processor, facilitateperformance of operations, comprising: assigning identifier data to agroup of policy node devices of a communication network, wherein thegroup of policy node devices is used to establish an applicationservice, wherein the identifier data represents a first node identifierassigned to a packet data network gateway device and a second nodeidentifier assigned to a policy node device of the group of policy nodedevices, and wherein the second node identifier is returned by thepolicy node device to the packet data network gateway device in a creditcontrol answer message; and in response to receiving, from a userequipment, request data indicative of a request to initiate theapplication service, inserting the identifier data within message datathat is transferred to a diameter routing agent device to enableselection of the policy node device of the group of policy node devicesand associated with the user equipment, wherein the policy node deviceprovides information that is used to establish a dedicated bearerassociated with the application service.
 2. The system of claim 1,wherein the operations further comprise: during an establishment of adefault bearer, facilitating a transfer of the identifier data to thepacket data network gateway device, of the communication network, thatserves the user equipment.
 3. The system of claim 2, wherein theoperations further comprise: directing the identifier data from thepacket data network gateway device to an application function device ofthe communication network.
 4. The system of claim 3, wherein theidentifier data is directed from the packet data network gateway deviceto the application function device via out-of-band signaling.
 5. Thesystem of claim 3, wherein the operations further comprise: in responseto receiving the request data, directing the message data comprising theidentifier data from the application function device to the diameterrouting agent device via a diameter request.
 6. The system of claim 2,wherein the operations further comprise: directing the identifier datafrom the packet data network gateway device to the user equipment,wherein the identifier data is stored within a data store of the userequipment.
 7. The system of claim 6, wherein the request data comprisesthe identifier data.
 8. The system of claim 1, wherein the identifierdata comprises address data indicative of an address of the policy nodedevice.
 9. The system of claim 1, wherein the identifier data compriseshostname data indicative of a hostname of the policy node device. 10.The system of claim 1, wherein the identifier data comprises a definedidentifier that applies to a pool of the group of policy node devicesthat share a common session database.
 11. The system of claim 1, whereinthe identifier data comprises a defined identifier that maps to a firsthostname of packet data network gateway device of the communicationnetwork and to a second hostname of a policy and charging rules functiondevice of the communication network.
 12. A method, comprising: inresponse to determining that a default bearer has been established for auser equipment served by a communication network, receiving, by a systemcomprising a processor, identifier data indicative of a group of policynode devices of the communication network, wherein the group of policynode devices is used to establish an application service, wherein theidentifier data represents a first node identifier assigned to a packetdata network gateway device and a second node identifier assigned to apolicy node device of the group of policy node devices, and wherein thesecond node identifier is returned by the policy node device to thepacket data network gateway device in a credit control answer message;and in response to receiving, from the user equipment, request dataindicative of a request to initiate the application service, directing,by the system, message data to a diameter routing agent, wherein themessage data comprises the identifier data that is used to select thepolicy node device of the group of policy node devices, and wherein thedirecting facilitates a transfer of the message data to the policy nodedevice that provides information that is utilized to establish adedicated bearer associated with the application service.
 13. The methodof claim 12, further comprising: storing, by the system, the identifierdata, within a data store of the user equipment.
 14. The method of claim12, further comprising: storing, by the system, the identifier data,within a data store of an application function device of thecommunication network.
 15. A machine-readable storage medium, comprisingexecutable instructions that, when executed by a processor of a userequipment, facilitate performance of operations, comprising: receivingidentifier data indicative of a group of policy node devices of acommunication network, wherein the group of policy node devices isassociated with an establishment of a default bearer for the userequipment, wherein the identifier data represents a first nodeidentifier assigned to a packet data network gateway device and a secondnode identifier assigned to a policy node device of the group of policynode devices, and wherein the second node identifier is returned by thepolicy node device to the packet data network gateway device in a creditcontrol answer message; in response to determining that an applicationservice is to be initiated, determining request data indicative of arequest to initiate the application service; wherein the request datacomprises the identifier data; and directing the request data to anapplication function device of the communication network, wherein thedirecting facilitates a transfer of message data to the group of policynode devices to facilitate an establishment of a dedicated bearer forthe application service.
 16. The machine-readable storage medium ofclaim 15, wherein the identifier data comprises a defined identifierthat maps to a first hostname of the packet data network gateway deviceof the communication network and to a second hostname of a policy andcharging rules function device of the communication network.
 17. Themachine-readable storage medium of claim 15, wherein the request data istransferred to a diameter routing agent device of the communicationnetwork, and wherein the identifier data is used to determine hostnamedata associated with a policy and charging rules function device, of thecommunication network, to which the request data is to be relayed. 18.The machine-readable storage medium of claim 17, wherein the hostnamedata is determined based on information stored within a mapping table ofthe diameter routing agent device.
 19. The machine-readable storagemedium of claim 15, wherein the application service comprises a voiceover long term evolution call.
 20. The machine-readable storage mediumof claim 15, wherein the directing facilitates the transfer of themessage data to the group of policy node devices independent ofemploying a binding database.